home *** CD-ROM | disk | FTP | other *** search
- Hints and Tips
- 7.5
- • CC Turbo & Laser Direct Drivers − A few people have discovered a
- problem that occurs when you try to run the RISC OS !Printers after
- having run a Turbo Driver or a Laser Direct driver. The error “Module
- PDriver 3.16 or later is required” appears. To clear this, do a
- *RMReinit PDriver before using the Acorn driver.
- 7.5
- • File copying on floppies − When copying from one floppy to another,
- the overall copy time can be reduced by opening the task manager and
- dragging the Next slot to 800Kb (or 1600Kb for an HD disc if you have
- the memory). This means that the next task to request space (i.e. the
- filer) will have enough space to read in the entire contents of one
- floppy, so that you don’t have to swap discs more than once.
- 7.5
- On large copy jobs (say between two hard discs) the larger area the
- filer gets, the faster the copying because fewer reading/writing cycles
- will be needed. You can either adjust the Next slot or, once copying has
- begun, drag out the Filer Action Window task as large as it will go.
- When copying is complete, the space is regained.
- 7.5
- • Floptical drives and faulty floppies − An article in a German PC
- magazine claimed that, due to their much more elaborate construction,
- flopticals drives could handle many discs which caused normal floppy
- drives to give up; I can report to all floptical owners that this claim
- holds true for the Acorn world, too.
- 7.5
- A software upgrade arrived on a disc which my floppy drive could not
- read − a disc error 08 was reported and Verify found a massive 56
- defects! My floptical drive, however, had no problem at all with the
- disc − it verified OK and the software could be loaded and runs
- perfectly. So, when the readability of a disc is a borderline case,
- giving the disc to the floptical drive to read might well help. Jochen
- Konietzko, Köln, Germany
- 7.5
- • Printer driver problem − “SWI &42940 Not known”. This error was
- reported recently in another printer driver problem. A quick look at the
- PRM showed this to be a BufferManager SWI. The buffer module had become
- unplugged which was causing the problems. It is not such an obvious
- problem though because the error appears to come from the printer
- driver. The solution is to press <f12> and type *RMReinit BufferManager
- <return> and then another <return> to get back to the desktop. A
- 7.5
-